bin/cli.js (1)

449-485: CLI UX mismatch: PR says run-test -b, code implements run-test -p (and dev-mode uses -b).

Given the PR objective/example, I’d align the short flag across commands (or update docs). If you want -b everywhere:

-  .option("-p, --pattern <pattern>", "Run all tests that match this pattern (optional)", "")
+  .option("-b, --pattern <pattern>", "Run all tests that match this pattern (optional)", "")

Also: consider making the action async and await the runner calls to avoid unhandled rejections / edge-case early exit:

-  .action((options) => {
+  .action(async (options) => {
@@
-      liquidTestRunner.runTestsStatusOnly(options.firm, templateType, templateName, options.test, options.pattern);
+      await liquidTestRunner.runTestsStatusOnly(options.firm, templateType, templateName, options.test, options.pattern);
@@
-      liquidTestRunner.runTestsWithOutput(options.firm, templateType, templateName, options.test, options.previewOnly, options.htmlInput, options.htmlPreview, options.pattern);
+      await liquidTestRunner.runTestsWithOutput(options.firm, templateType, templateName, options.test, options.previewOnly, options.htmlInput, options.htmlPreview, options.pattern);
     }
   });

lib/liquidTestRunner.js (1)

103-193: Block testName + pattern at the library boundary (not just CLI).

If a non-CLI caller passes both, you’ll set tests: filteredContent but compute test_line from the unfiltered testIndexes, which can point to the wrong line. Add a guard:

 function buildTestParams(firmId, templateType, handle, testName = "", renderMode, pattern = "") {
+  if (testName && pattern) {
+    consola.error("You cannot use both testName and pattern at the same time");
+    process.exit(1);
+  }
   let relativePath = `./reconciliation_texts/${handle}`;

lib/liquidTestRunner.js (2)

20-32: findTestRows() key matching is unsafe (substring collisions) → can select wrong tests / wrong line numbers.

findTestRows() uses element.includes(testName) (Line 28). This will mis-detect YAML key lines when:

• one test name is a substring of another (unit_1 matches unit_10:),
• the test name appears in a value or comment before the key,
• quoting/formatting varies.

That breaks filterTestsByPattern() segmentation (Line 44-79), test_line computation (Line 193), and lineAdjustments (Line 87-93).

Suggested fix: match YAML keys at line start (optionally quoted) instead of substring search.

 function findTestRows(testContent) {
   const options = { maxAliasCount: 10000 };
   const testYAML = yaml.parse(testContent, options);

   const testNames = Object.keys(testYAML);
   const testRows = testContent.split("\n");
   const indexes = {};
+
+  const escapeRegExp = (s) => s.replace(/[.*+?^${}()|[\]\\]/g, "\\$&");
   testNames.forEach((testName) => {
-    const index = testRows.findIndex((element) => element.includes(testName));
+    const keyRe = new RegExp(`^\\s*["']?${escapeRegExp(testName)}["']?\\s*:\\s*(#.*)?$`);
+    const index = testRows.findIndex((line) => keyRe.test(line));
     indexes[testName] = index;
   });
   return indexes;
 }

(If you need to support testName followed by inline YAML (key: { ... }), the regex still works.)

Also applies to: 34-101

---

103-196: Add testName XOR pattern guard to buildTestParams()

While the CLI prevents using both --test and --pattern together, the constraint should be enforced at the function level rather than relying solely on CLI validation. If buildTestParams() is called with both testName and pattern, finalTests gets filtered by pattern (lines 133–145) but testParams.test_line references the original testIndexes (line 193), causing a mismatch where the line number may target the wrong test.

Add this guard at the start of buildTestParams():

 function buildTestParams(firmId, templateType, handle, testName = "", renderMode, pattern = "") {
+  if (testName && pattern) {
+    consola.error("You cannot use both testName and pattern at the same time");
+    process.exit(1);
+  }
   let relativePath = `./reconciliation_texts/${handle}`;